Skip to content

DATACMNS-1833 - Revise documentation for query method keywords. #477

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
wants to merge 3 commits into from

Conversation

mp911de
Copy link
Member

@mp911de mp911de commented Nov 20, 2020

Related ticket: DATACMNS-1833.

@mp911de mp911de closed this Dec 1, 2020
@mp911de mp911de deleted the issue/DATACMNS-1833 branch December 1, 2020 08:51
mp911de added a commit that referenced this pull request Dec 1, 2020
mp911de added a commit that referenced this pull request Dec 1, 2020
Reformat asciidoc.

Original pull request: #477.
mp911de added a commit that referenced this pull request Dec 1, 2020
mp911de added a commit that referenced this pull request Dec 1, 2020
Reformat asciidoc.

Original pull request: #477.
mp911de added a commit that referenced this pull request Dec 1, 2020
mp911de added a commit that referenced this pull request Dec 1, 2020
Reformat asciidoc.

Original pull request: #477.
|===============
|Keyword | Description
|`find…By`, `read…By`, `get…By`, `query…By`, `search…By`, `stream…By`| General query method returning typically the repository type, a `Collection` or `Streamable` subtype or a result wrapper such as `Page`, `GeoResults` or any other store-specific result wrapper.
|`exists…By`| Exists projection, returnung typically a `boolean` result.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Typo: "Returning" misspelled as "returnung" both here and in the next line.

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Good catch. That's fixed in the merge commits.

@@ -27,7 +31,7 @@ NOTE: Geospatial types (such as `GeoResult`, `GeoResults`, and `GeoPage`) are av
|`Future<T>`|A `Future`. Expects a method to be annotated with `@Async` and requires Spring's asynchronous method execution capability to be enabled.
|`CompletableFuture<T>`|A Java 8 `CompletableFuture`. Expects a method to be annotated with `@Async` and requires Spring's asynchronous method execution capability to be enabled.
|`ListenableFuture`|A `org.springframework.util.concurrent.ListenableFuture`. Expects a method to be annotated with `@Async` and requires Spring's asynchronous method execution capability to be enabled.
Copy link

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks like this one should be generic as well: ListenableFuture<T>.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

3 participants